Skip to content

Upgrade Elastic to version 9+ #1023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
akatsoulas opened this issue May 4, 2022 · 3 comments
Open

Upgrade Elastic to version 9+ #1023

akatsoulas opened this issue May 4, 2022 · 3 comments
Assignees
Labels

Comments

@akatsoulas
Copy link
Collaborator

No description provided.

@smithellis
Copy link
Collaborator

It looks like our usage of elasticsearch-dsl is holding us back on this - it doesn't have a release candidate for 8+ yet. elastic/elasticsearch-dsl-py#1569

@akatsoulas akatsoulas moved this to Todo in Mozilla Support Jun 27, 2023
@smithellis smithellis moved this from 🗄 backlog to 🚀 in progress in Mozilla Support Apr 30, 2025
@smithellis smithellis self-assigned this Apr 30, 2025
@smithellis
Copy link
Collaborator

mozilla/kitsune#6640

@smithellis smithellis moved this from 🚀 in progress to 📚 review in Mozilla Support May 6, 2025
@smithellis smithellis moved this from 📚 review to 🚀 in progress in Mozilla Support May 6, 2025
@smithellis smithellis moved this from 🚀 in progress to Blocked in Mozilla Support May 23, 2025
@akatsoulas akatsoulas moved this from Blocked to 🚀 in progress in Mozilla Support Jun 2, 2025
@smithellis smithellis changed the title Upgrade Elastic to version 8+ Upgrade Elastic to version 9+ Jun 2, 2025
@smithellis
Copy link
Collaborator

Here is what I know.
I have two branches, one to take us from 7.17 to 8+, and one to go from 8 to 9.
Locally, these both function, returning search results as expected (if you make sure to es_init, es_reindex and start a celery worker).
In Elastic proper, in dev, after the migration of the server, results are not populated as expected. We appear to be returning the count of results properly, but not the actual content of the results. I believe that during the migration, I either selected a poor option for index handling, or something just got corrupted in the migration. To complicate things, I was unable to roll dev back at Elastic without issue, and I'm unclear if some of the choices I'm available to me carry risks. I'd like to replace dev at elastic with the content of stage at Elastic. Then I could re-do the migrations again and rule out some potential issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🚀 in progress
Development

No branches or pull requests

2 participants